@sagalbot any thoughts on getting this in as well as #1093? I ask because my project is currently using a fork that has the functionality in place. Let me know if you need me to do anything else with this work. Thanks!

@dkurucz just had a chance to check it out today. My first instinct is that this should actually be default behavior.

This default behavior feels like a bug to me:

And with enableMouseSearchInput:

I can't think of a use case where enableMouseSearchInput should be false. You can still click the caret to close (although it should probably have cursor: pointer on hover). I think chances of people finding the right prop to enable this behavior is also fairly low.

Do you agree that enableMouseSearchInput should just be default behavior? If so, lets drop the prop and implement it as such, and I'll push it out as a patch release.

This is a bit related to what I was working on in #1067.

@sagalbot yes I agree with your thoughts on this. I think it might be better to have the opposite as an option, where it would close on click only if the user is expected to pick an option discreetly. There is a case in my project right now where that could be the preferred behavior. I would equate this to a "choose one of the following" type of input, where you also wouldn't even want the user to type to search. However, at this point it would be a nice to have.

If you'd like, I'll take another pass and get it working by default and then put up a proposal for the flag (or maybe a PR if I can get it all in one go).

@sagalbot I have removed the flag and made the behavior default, feel free to re-test, etc, I think this is largely good to go. Let me know if you have other thoughts on this. Thanks!

@sagalbot any thoughts on a timeline to get this feature in? thanks!

@dkurucz should go out this morning!

🎉 This PR is included in version 3.10.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

This functionality breaks the use of a router-link in "selected-option" slot like this :

<template v-slot:selected-option="customerScope">
    <router-link class="mr-2" :to="{ name: 'customer', params: { id: customerScope.id } }">
        {{ customerScope.name }}
    </router-link>
</template>

This shouldn't be enabled by default.

Then, I don't see any reference of enableMouseSearchInput in code or documentation.

Finally, there is a mispelling in jest test (enableMouseInputSearch instead of enableMouseSearchInput)

@MoogyG I'll look into the router link issue when I have a moment. In regards to your other concerns, this issue was accepted as default behavior (it was originally coded as an option), as a result no option was included or configured to enable/disable this behavior, so there will be no additions to the documentation about it. The unit test was an oversight, and should be removed since we are no longer testing the option. We will of course want to enhance some other unit test that is in the main line, reusing some of the test, to ensure the default behavior is in fact default, however.

@MoogyG I tested and fixed your above concerns in the following PR: #1211. Feel free to test on your end as well.

I just get your PR, build it locally, copy "dist" folder in my node_modules but it's not working on my machine, I still can't click on a router link inside vue-select.

@MoogyG can you verify you also copied the compiled css in addition to the built js into the dist directory of node_modules vue-select? Both are required in that fix. If so, can you send me a screenshot of what you are seeing? Let's also move this discussion to the new PR. Thanks!

My bad, I was importing SCSS from src folder, not CSS from dist folder.
Now it works, thanks for your support!